After completing this lesson, you’ll be able to:
Let's start our tour of the FME Flow web interface at the Run Workspace page. You can access it from the corresponding menu option:
This opens the Run Workspace page, where you can choose a repository, workspace, and service to run a translation:
When you select a workspace that contains Published Parameters, those parameters will be available to be set before running the translation.
The Run Workspace page in FME Flow also has an additional section under Advanced. Clicking the arrow to the right of Advanced will expand the advanced parameters menu. These are FME Flow specific parameters that fine-tune how the workspace will be run.
Job Queue
Job Queues provide a way to send FME Flow jobs to specific Engines or to control the priority of job requests. This parameter allows you to select a predefined Queue to which this job should be sent when it is run. Job Queues can be created by an FME Flow Administrator from the Engine Management page.
Queued Job Expiry Time
This sets the maximum amount of time a job can wait in the Queued state before being run. If a job waits longer than this amount of time in the Queue, it will not be run. This option is useful for time-sensitive jobs that you do not want to run after the specified time is exceeded.
Running Job Expiry Time
This sets the maximum amount of time a job can stay in the running state. When this time is exceeded, the job will be cancelled automatically.
Other Ways to Run this Workspace
Additionally, in the Advanced section, you can create an FME Flow App or create a webhook to run your workspace.
When you are satisfied with the parameters, click the green Run button at the bottom of the page to run the translation. A progress dialog will appear, indicating whether your workspace is Running or Queued. From this dialog you can cancel the job or view the details:
Once the workspace (job) has finished running, a completion message will appear, letting you know whether the translation was successful or if it failed. Depending on the Service you ran the workspace with, you will also see other details such as a download link:
Note that there are other ways to find and run a workspace. Recently published workspaces and workspaces "starred" as a favorite can be easily found on the interface landing page.
Additionally, it's possible to browse for a workspace to run by going through the Workspaces page, which is more like a file browser than a simple selection tool.
Jobs are submitted to the FME Flow core, which then assigns them to engines. Having more engines means you can run more jobs simultaneously. Learn more.
Information about all jobs that are running or have run on FME Flow will be stored so you can easily view activity on FME Flow. To access this, choose the menu option for Jobs and select Completed, Queued, or Running jobs to view:
This opens the Jobs page, where you can see the status of jobs, whether Completed, Queued, or Running:
This allows you to check that the translation you just ran finished successfully.
The Filters menu at the top allows you to filter by User, Status, Engine, Repository, Workspace, Source Type, and Source Name. This is especially useful when the job history table runs to thousands of jobs. Filtering helps to find information about a specific job or, for example, to quickly find all jobs that resulted in a failure message.
Clicking on a completed job opens up a page showing information about that job; such as User, Status, Engine, Repository, Workspace, Source Type, and Source Name. You can also view, filter, and search the job log.
A series of buttons allow you to download the FME log from the translation, resubmit the job with a single click, view the workspace, and download the workspace:
This allows you to confirm that the workspace functioned correctly, with the same level of detail as you could find within FME Form.
Queued and Running jobs can be listed so that you can see what jobs FME Flow is currently handling. You can filter the jobs by a particular username.
One particularly useful feature is that these pages can be used to cancel jobs if they are no longer required.
If your jobs are being queued regularly, talk to your FME Flow Administrator about different options like Job Queues, dedicated engines, or scheduling larger tasks to run outside of regular office hours.
